Fix VNC server after HVM save/restore/migrate, when no vncpasswd specified.
authorkfraser@localhost.localdomain <kfraser@localhost.localdomain>
Tue, 28 Aug 2007 14:58:46 +0000 (15:58 +0100)
committerkfraser@localhost.localdomain <kfraser@localhost.localdomain>
Tue, 28 Aug 2007 14:58:46 +0000 (15:58 +0100)
commit145dd4e0fb588f095e45d954abe3ebcc5327ae54
tree5a96addca8781db20f365250e6f2189e98f1e563
parent62ba102d87382483324ed98556fe735c7fe2dd30
Fix VNC server after HVM save/restore/migrate, when no vncpasswd specified.

The basic problem was that the "image" section of the sxp had a "None"
in it, which means that on the restore (either on the local machine or
remote machine), the vnc server in the qemu device model literally
needed the string "None" to properly connect.  This simple patch only
puts a vncpasswd entry in the image if it is *not* None in the python
code, thus avoiding the whole issue.

Signed-off-by: Chris Lalancette <clalance@redhat.com>
tools/python/xen/xm/create.py